Context-free document portions with alternate formats

ABSTRACT

Self-describing portions of text or data are provided for associating with or inserting in a computer-generated document. Portions of a document, such as individual paragraphs or groups of paragraphs or fragments of text, are provided self-describing properties, such as file format type associated with the portion, style, font, list type, and the like. If such a portion of a document is subsequently linked to or copied or moved to a second document or to a different location in a first document, the self-describing properties provided for the portion travel with the portion to the second document or to the different location in the first document. An application receiving the content portion may consume and display the portion according to the properties provided for the portion.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present invention is a continuation-in-part and claims priority to U.S. patent application Ser. No. 10/731,900, filed Dec. 9, 2003, entitled “Context Free Document Portions,” which is incorporated herein by reference as if fully set out herein.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the U.S. Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

FIELD OF THE INVENTION

The present invention generally relates to managing data across different computer-generated documents. More particularly, the present invention relates to utilization of context-free document portions having alternate formats and other properties in association with a single computer-generated document.

BACKGROUND OF THE INVENTION

With the advent of the computer age, computer and software users have grown accustomed to user-friendly software applications that help then write, calculate, organize, prepare presentations, send and receive electronic mail, make music, and the like. For example, modern electronic word processing applications allow users to prepare a variety of useful documents. Modem spreadsheet applications allow users to enter, manipulate, and organize data. Modem electronic slide presentation applications allow users to create a variety of slide presentations containing text, pictures, data or other useful objects.

Methods and systems have been developed for representing documents and associated properties generated by such applications according to various formatting types. For example, documents may be represented in binary format, Hypertext Markup Language (HTML) format, rich text format (RTF), Extensible Markup Language format (XML), and the like. In addition, there are many components that make up such documents, including paragraphs, tables, styles, fonts, lists and the like. Some components of a document reference other components for providing a first component with structural limitations. For example, a paragraph in a document might reference a particular formatting type or style setting that defines how the paragraph is to appear in a document. For another example, a paragraph component of a document may be part of a particular list structure in a document. Because there are a number of properties and objects that other objects of a document may reference, such as styles, there is typically a need in a document for a header in which various properties and objects, such as styles and font definitions, are located.

Unfortunately, a problem occurs when a user attempts to add additional content to a particular document, for example, a paragraph, text portion, image, chart, and the like, where the additional content is formatted according to a formatting that is different from the formatting of the document to which the additional content is being added. For example, a given application may store all rich text in HTML format. To take content from a document generated by that application to a non-HTML application, the HTML-formatted content must be transformed into another format. Otherwise, if the HTML-formatted content, for example, is added to a document formatted according to another formatting, for example, XML, the original formatting of the added content may be lost, or the additional content may fail to load altogether.

It is with respect to these and other considerations that the present invention has been made.

SUMMARY OF THE INVENTION

The present invention solves the above and other problems by providing self-describing portions of text or data in a document. According to an embodiment of the invention, portions of a document, such as individual paragraphs or groups of paragraphs or fragments of text, are provided self-describing properties such as file format type associated with the portion, style, font, list type, and the like. If such a portion of a document is subsequently copied or moved to a second document or to a different location in the first document, the self-describing properties provided for the portion travel with the portion to the second document or to the different location in the first document. Consequently, an application preparing and displaying the second document or the first document may consume and display the portion according to the properties provided for the portion.

According to another embodiment, a document container is established for displaying and editing a document. Self-describing portions or components of the document may be maintained and edited in the document container. Alternatively, the self-describing portions or components of the document may be maintained and edited separately from the document container, but may be pointed to from within the document container. At open time for the document, all document portions or components pointed to from within the document container may be merged by and displayed by an application enabled to consume each of the different document portions or components according to their individual file format types or other properties.

These and other features, advantages, and aspects of the present invention may be more clearly understood and appreciated from a review of the following detailed description of the disclosed embodiments and by reference to the appended drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified block diagram of a computing system and associated peripherals and network devices that provide an exemplary operating environment for the present invention.

FIG. 2 is a simplified block diagram illustrating interaction between software objects according to an object-oriented programming model.

FIG. 3 is a block diagram illustrating interaction between a document, an attached schema file, and a schema validation functionality model.

FIG. 4 is a block diagram illustrating interaction between a first document and a second document where a portion of text is copied or moved from the second document to the first document according to embodiments of the present invention.

FIG. 5 is a block diagram illustrating interaction between a first document and a second document where a portion of text is copied or moved from the second document to the first document according to embodiments of the present invention.

FIG. 6 is a simplified block diagram illustrating the insertion of context-free document portions or components having self-described alternative file formats into an XML-based document according to embodiments of the present invention.

FIG. 7 is a simplified block diagram illustrating an XML-based document referencing context-free document portions or components having different or alternative file formats for merging with the XML-based document according to embodiments of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

As briefly described above, embodiments of the present invention are directed to methods and systems for inserting or referencing portions of text or data into or by a document where the inserted or referenced portions of text or data are formatted according to a file format type and other properties different from the document into which the portions of text or data are inserted or to which the portions of text or data are referenced for merger with the receiving document. These embodiments may be combined, other embodiments may be utilized, and structural changes may be made without departing from the spirit or scope of the present invention. The following detailed description is therefore not to be taken in a limiting senses and the scope of the present invention is defined by the appended claims and their equivalents.

Referring now to the drawings, in which like numerals represent like elements through the several figures, aspects of the present invention and the exemplary operating environment will be described. FIG. 1 and the following discussion are intended to provide a brief, general description of a suitable computing environment in which the invention may be implemented. While the invention will be described in the general context of program modules that execute in conjunction with an application program that runs on an operating system on a personal computer, those skilled in the art will recognize that the invention may also be implemented in combination with other program modules.

Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

Turning now to FIG. 1, illustrative computer architecture for a personal computer 2 for practicing the various embodiments of the invention will be described. The computer architecture shown in FIG. 1 illustrates a conventional personal computer, including a central processing unit 4 (“CPU”), a system memory 6, including a random access memory 8 (“RAM”) and a read-only memory (“ROM”) 10, and a system bus 12 that couples the memory to the CPU 4. A basic input/output system containing the basic routines that help to transfer information between elements within the computer, such as during startup, is stored in the ROM 10. The personal computer 2 further includes a mass storage device 14 for storing an operating system 16, application programs, such as the application program 305, and data.

The mass storage device 14 is connected to the CPU 4 through a mass storage controller (not shown) connected to the bus 12. The mass storage device 14 and its associated computer-readable media, provide non-volatile storage for the personal computer 2. Although the description of computer-readable media contained herein refers to a mass storage device, such as a hard disk or CD-ROM drive, it should be appreciated by those skilled in the art that computer-readable media can be any available media that can be accessed by the personal computer 2.

By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, DVD, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer.

According to various embodiments of the invention, the personal computer 2 may operate in a networked environment using logical connections to remote computers through a TCP/IP network 18, such as the Internet. The personal computer 2 may connect to the TCP/IP network 18 through a network interface unit 20 connected to the bus 12. It should be appreciated that the network interface unit 20 may also be utilized to connect to other types of networks and remote computer systems. The personal computer 2 may also include an input/output controller 22 for receiving and processing input from a number of devices, including a keyboard or mouse (not shown). Similarly, an input/output controller 22 may provide output to a display screen, a printer, or other type of output device.

As mentioned briefly above, a number of program modules and data files may be stored in the mass storage device 14 and RAM 8 of the personal computer 2, including an operating system 16 suitable for controlling the operation of a networked personal computer, such as the WINDOWS XP operating system from MICROSOFT CORPORATION of Redmond, Wash. The mass storage device 14 and RAM 8 may also store one or more application programs. In particular, the mass storage device 14 and RAM 8 may store an application program 305 for creating and editing an electronic document 310. For instance, the application program 305 may comprise a word processing application program, a spreadsheet application, a contact application, and the like. Application programs for creating and editing other types of electronic documents may also be used with the various embodiments of the present invention. A schema file 330 and a namespace/schema library 400, described below, are also shown.

Exemplary embodiments of the present invention are implemented by communications between different software objects in an object-oriented programming environment. For purposes of the following description of embodiments of the present invention, it is useful to briefly to describe components of an object-oriented programming environment. FIG. 2 is a simplified block diagram illustrating interaction between software objects according to an object-oriented programming model. According to an object-oriented programming environment, a first object 210 may include software code, executable methods, properties, and parameters. Similarly, a second object 220 may also include software code, executable methods, properties, and parameters.

A first object 210 may communicate with a second object 220 to obtain information or functionality from the second object 220 by calling the second object 220 via a message call 230. As is well know to those skilled in the art of object-oriented programming environment, the first object 210 may communicate with the second object 220 via application programming interfaces (API) that allow two disparate software objects 210, 220 to communicate with each other in order to obtain information and functionality from each other. For example, if the first object 210 requires the functionality provided by a method contained in the second object 220, the first object 210 may pass a message call 230 to the second object 220 in which the first object identifies the required method and in which the first object passes any required parameters to the second object required by the second object for operating the identified method. Once the second object 220 receives the call from the first object, the second object executes the called method based on the provided parameters and sends a return message 250 containing a value obtained from the executed method back to the first object 210.

For example, in terms of embodiments of the present invention, and as will be described below, a first object 210 may be a third party customized application that passes a message to a second object such as an Extensible Markup Language schema validation object whereby the first object identifies a method requiring the validation of a specified XML element in a document where the specified XML element is a parameter passed by the first object with the identified method. Upon receipt of the call from the first object, according to this example, the schema validation object executes the identified method on the specified XML element and returns a message to the first object in the form of a result or value associated with the validated XML element. Operation of object-oriented programming environments, as briefly described above, are well known to those skilled in the art.

As described below, embodiments of the present invention are implemented through the interaction of software objects in the use, customization, and application of components of the Extensible Markup Language (XML). FIG. 3 is a block diagram illustrating interaction between a document, an attached schema file, and a schema validation functionality module. As is well known to those skilled in the art, the Extensible Markup Language (XML) provides a method of describing text and data in a document by allowing a user to create tag names that are applied to text or data in a document that in turn define the text or data to which associated tags are applied. For example referring to FIG. 3, the document 310 created with the application 305 contains text that has been marked up with XML tags 315, 320, 325. For example, the text “Greetings” is annotated with the XML tag <title>. The text “My name is Sarah” is annotated with the <body> tag. According to XML, the creator of the <title> and <body> tags is free to create her own tags for describing the tags to which those tags will be applied. Then, so long as any downstream consuming application or computing machine is provided instructions as to the definition of the tags applied to the text, that application or computing machine may utilize the data in accordance with the tags. For example, if a downstream application has been programmed to extract text defined as titles of articles or publications processed by that application, the application may parse the document 310 and extract the text “Greetings,” as illustrated in FIG. 3 because that text is annotated with the tag <title>. The creator of the particular XML tag naming for the document 310, illustrated in FIG. 3, provides useful description for text or data contained in the document 310 that may be utilized by third parties so long as those third parties are provided with the definitions associated with tags applied to the text or data.

According to embodiments of the present invention, the text and XML markup entered into the document 310 may be saved according to a variety of different file formats and according to the native programming language of the application 305 with which the document 310 is created. For example, the text and XML markup may be saved according to a word processing application, a spreadsheet application, and the like. Alternatively, the text and XML markup entered into the document 310 may be saved as an XML format whereby the text or data, any applied XML markup, and any formatting such as font, style, paragraph structure, etc. may be saved as an XML representation. Accordingly, downstream or third party applications capable of understanding data saved as XML may open and consume the text or data thus saved as an XML representation. For a detailed discussion of saving text and XML markup and associated formatting and other attributes of a document 310 as XML, see U.S. patent application entitled “Word Processing Document Stored in a Single XML File that may be Manipulated by Applications that Understanding XML,” U.S. Ser. No. 10/187,060, filed Jun. 28, 2002, which is incorporated herein by reference as if fully set out herein. An exemplary schema in accordance with the present invention is disclosed beginning on page 11 in an application entitled “Mixed Content Flexibility,” Ser. No. 10/726,077, filed Dec. 2, 2003, which is hereby incorporated by reference in its entirety.

In order to provide a definitional framework for XML markup elements (tags) applied to text or data, as illustrated in FIG. 3, XML schema files are created which contain information necessary for allowing users and consumers of marked up and stored data to understand the XML tagging definitions designed by the creator of the document. Each schema file also referred to in the art as a Namespace or XSD file preferably includes a listing of all XML elements (tags) that may be applied to a document according to a given schema file. For example, a schema file 330, illustrated in FIG. 3, may be a schema file containing definitions of certain XML elements that may be applied to a document 310 including attributes of XML elements or limitations and/or rules associated with text or data that may be annotated with XML elements according to the schema file. For example, referring to the schema file 330 illustrated in FIG. 3, the schema file is identified by the Namespace “intro”335 the schema file includes a root element of <intro card>.

According to the schema file 330, the <intro card> element serves as a root element for the schema file and also as a parent element to two child elements <title> and <body>. As is well known to those skilled in the art, a number of parent elements may be defined under a single root element, and a number of child elements may be defined under each parent element. Typically, however, a given schema file 330 contains only one root element. Referring still to FIG. 3, the schema file 330 also contains attributes 340 and 345 to the <title> and <body> elements, respectfully. The attributes 340 and 345 may provide further definition or rules associated with applying the respective elements to text or data in the document 310. For example, the attribute 345 defines that text annotated with the <title> element must be less than or equal to twenty-five characters in length. Accordingly, if text exceeding twenty-five characters in length is annotated with the <title> element or tag, the attempted annotation of that text will be invalid according to the definitions contained in the schema file 330.

By applying such definitions or rules as attributes to XML elements, the creator of the schema may dictate the structure of data contained in a document associated with a given schema file. For example, if the creator of a schema file 330 for defining XML markup applied to a resume document desires that the experience section of the resume document contain no more than four present or previous job entries, the creator of the schema file 330 may define an attribute of an <experience> element, for example, to allow that no more than four present or past job entries may be entered between the <experience> tags in order for the experience text to be valid according to the schema file 330. As is well known to those skilled in the art, the schema file 330 may be attached to or otherwise associated with a given document 310 for application of allowable XML markup defined in the attached schema file to the document 310. According to one embodiment, the document 310 marked up with XML elements of the attached or associated schema file 330 may point to the attached or associated schema file by pointing to a uniform resource identifier (URI) associated with a Namespace identifying the attached or associated schema file 330.

According to embodiments of the present invention, a document 310 may have a plurality of attached schema files. That is, a creator of the document 310 may associate or attach more than one schema file 330 to the document 310 in order to provide a framework for the annotation of XML markup from more than one schema file. For example, a document 310 may contain text or data associated with financial data. A creator of the document 310 may wish to associate XML schema files 330 containing XML markup and definitions associated with multiple financial institutions. Accordingly, the creator of the document 310 may associate an XML schema file 330 from one or more financial institutions with the document 310. Likewise, a given XML schema file 330 may be associated with a particular document structure such as a template for placing financial data into a desirable format.

According to embodiments of the present invention, a collection of XML schema files and associated document solutions may be maintained in a Namespace or schema library located separately from the document 310. The document 310 may in turn contain pointers to URIs in the Namespace or schema library associated with the one or more schema files attached to otherwise associated with the document 310. As the document 310 requires information from one or more associated schema files, the document 310 points to the Namespace or schema library to obtain the required schema definitions. For a detailed description of the use of an operation of Namespace or schema libraries, see U.S. patent application entitled “System and Method for Providing Namespace Related Information,” U.S. Ser. No. 10/184,190, filed Jun. 27, 2002, and U.S. patent application entitled “System and Method for Obtaining and Using Namespace Related Information for Opening XML Documents,” U.S. Ser. No. 10/185,940, filed Jun. 27, 2002, both U.S. patent applications of which are incorporated herein by reference as if fully set out herein. For a detailed description of a mechanism for downloading software components such as XML schema files and associated solutions from a Namespace or schema library, see U.S. patent application entitled Mechanism for Downloading Software Components from a Remote Source for Use by a Local Software Application, U.S. Ser. No. 10/164,260, filed Jun. 5, 2002.

Referring still to FIG. 3, a schema validation functionality module 350 is illustrated for validating XML markup applied to a document 310 against an XML schema file 330 attached to or otherwise associated with the document 310, as described above. As described above, the schema file 330 sets out acceptable XML elements and associated attributes and defines rules for the valid annotation of the document 310 with XML markup from an associated schema file 330. For example, as shown in the schema file 330, two child elements <title> and <body> are defined under the root or parent element <intro card>. Attributes 340, 345 defining the acceptable string length of text associated with the child elements <title> and <body> are also illustrated. As described above, if a user attempts to annotate the document 310 with XML markup from a schema file 330 attached to or associated with the document in violation of the XML markup definitions contained in the schema file 330, an invalidity or error state will be presented. For example, if the user attempts to enter a title string exceeding twenty-five characters, that text entry will violate the maximum character length attribute of the <title> element of the schema file 330. In order to validate XML markup applied to a document 310, against an associated schema file 330, a schema validation module 350 is utilized. As should be understood by those skilled in the art, the schema validation module 350 is a software module including computer executable instructions sufficient for comparing XML markup and associated text entered in to a document 310 against an associated or attached XML schema file 330 as the XML markup and associated text is entered in to the document 310.

According to embodiments of the present invention, the schema validation module 350 compares each XML markup element and associated text or data applied to the document 310 against the attached or associated schema file 330 to determine whether each element and associated text or data complies with the rules and definitions set out by the attached schema file 330. For example, if a user attempts to enter a character string exceeding twenty-five characters annotated by the <title> elements 320, the schema validation module will compare that text string against the text string attribute 340 of the attached schema file 330 and determine that the text string entered by the user exceeds the maximum allowable text string length. Accordingly, an error message or dialogue will be presented to the user to alert the user that the text string being entered by the user exceeds the maximum allowable character length according to the attached schema file 330. Likewise, if the user attempts to add an XML markup element between the <title> and the <body> elements, the schema validation module 350 will determine that the XML markup element applied by the user is not a valid element allowed between the <title> and <body> elements according to the attached schema file 330. Accordingly, the schema validation module 350 will generate an error message or dialogue to the user to alert the user of the invalid XML markup.

Context Free Document Text and Data Portions

As briefly described above, embodiments of the present invention provide methods and systems for inserting a portion of text or data into a document where the inserted portion of text or data carries with it its own specific formatting and style properties such as specified styles, fonts, list types, and the like. FIG. 4 is a block diagram illustrating interaction between a first document and a second document where a portion of text is copied or moved from the second document to the first document according to embodiments of the present invention. FIG. 5 is a block diagram illustrating interaction between a first document and a second document where a portion of text is copied or moved from the second document to the first document according to embodiments of the present invention. It should be understood that describing the present invention in terms of copying or moving a text portion from one document to another is by way example only. Apart from copying or moving text from one document to another, the self-describing properties of the text portion allow users and software applications who desire to or who are required to parse and manipulate a file to apply rich editing to portions of the file or document without having to parse the entire document to manage properties associated with the entire document or file.

Referring to FIG. 4, a document 410 and a document 420 are described for purposes of illustrating how a portion of text may be copied from the document 420 into the document 410 according to embodiments of the present invention. The first document 410 has a title 435 and two paragraphs 445 and 450. Also illustrated for the document 410 is an XML structure pane 425 showing Extensible Markup Language (XML) structure applied to the document 435. For example, a <title> element is applied to the title of the document 435, a <paragraph 1> element is applied to the first paragraph of the document 435 and a <paragraph 2> element is applied to the second paragraph of the document 435. The second document 420 includes a document 440 that has been similarly marked up with XML structure. An XML structure pane 430 is illustrated for the document 420.

According to embodiments of the present invention, a text or data portion from the second document may be copied or moved to the first document such that style and other formatting properties are carried with the text or data portion from the one document to another document. Accordingly, there is no need to resolve style or formatting properties associated with the text portion inserted into the first document against style or other formatting properties associated with the first document. For example, as shown in FIG. 4 the first document may have a header information properties element for referencing styles and other formatting properties associated with the first document. That is, the user or creator of the first document may have established a set of styles or formatting properties for the first document. According to prior art systems, as described above, if the user desires to copy the second paragraph 455 from the second document 420 into the first document 410, style or formatting information associated with the second paragraph 455 in the second document 420 may conflict with style or formatting information contained at the document level of the first document 410.

For example, the first document 410 may have a style called “Header 1” causing a formatting of boldface and italics to be applied to the document 435. On the other hand, the creator of the second document 420 may have likewise used the style designator “Header 1” for formatting the second paragraph 455 containing the second document to include boldfacing, but not italics. If the second paragraph 455 of the second document 420 is copied into the first document 410, the style applied to the second document will conflict with the style applied to the document in the first document 410. Therefore, the user of the first document 410 will be required to manually parse the header information properties element of the XML structure applied to the first document 410 in order to make changes to the styles applied to the inserted text or data in order to prevent a conflict of the two styles.

According to embodiments of the present invention, an XML schema is provided for applying style markup as specified text and data portions of a document such as the second paragraph 455 of the second document 420 so that particular styles or formatting applications to a given text or data portion are carried with the text or data portion to the first document. By applying an XML markup to a particular text or data selection, the first document need not de-conflict style or formatting properties applied to inserted text or data portions so long as the first document has access to the style or formatting markup applied to the inserted text or data portion.

Referring to FIG. 5, a text portion 510 and a text portion 520 are illustrated for inserting into the first document 410. According to embodiments of the present invention, each text portion 510 and 520 may be a sentence, a paragraph, multiple paragraphs, fragments of sentences or paragraphs, alphanumeric data, or any other native objects. As should be appreciated, the creator of the second document 420 marks up the second document with Extensible Markup Language data according to the context free text portion schema which defines XML elements, as described below, for specifying particular text or data portions which carries with them their own styles or other formatting properties. In effect, each of the text portions 510 and 520 become “mini” documents carrying their own style and formatting properties that may be inserted into a first document 410 and which may be treated separately from the main document 410 by an XML parsing application operating on the document 410.

It should be understood, a text or data portion such as the second paragraph 455 or either of the text portions 510, 520 illustrated in FIG. 5, may be copied and pasted or cut and pasted from the second document into the first document according to conventional cut/copy and pasting methods available from a variety of software applications. Alternatively, according to a variety of Extensible Markup Language parsing applications, the user may likewise insert a text or data portion from a second document into a first document by selecting an appropriate XML node from the XML structure pane 430 and copying that XML node into the XML structure of the first document. That is, by selecting the <paragraph 2> node 460 from the XML structure 430 of the second document 420 and by moving that node to the XML structure of the first document 410, the XML markup and associated text or data of the second paragraph 455 may be inserted into the first document along with its own style and other formatting properties as described herein.

To further illustrate the operation of embodiments of the present invention, the following XML structure is associated with a simple document having the following two paragraphs.

Para 1: The quick brown fox jumps over the lazy dog.

Para 2: The quick brown fox jumps over the lazy dog.

As can be seen in the following XML structure, a font of “Times New Roman” and a style identification of “Default Paragraph Font” is applied to the two paragraphs. The actual text of the two paragraphs is also illustrated in the following XML structure.

<?xml version=“1.0” encoding=“UTF-8” standalone=“yes” ?> −<w:wordDocument xmlns:w=“http://schemas.microsoft.com/office/word/2003/wordml” xmlns:wx=“http://schemas.microsoft.com/office/word/2003/auxHint” w:macrosPresent=“no”  w:embeddedObjPresent=“no”  w:ocxPresent=“no” xml:space=“preserve”>   −<w:styles> <w:versionOfBuiltInStylenames w:val=“4” /> <w:latentStyles w:defLockedState=“off w:latentStyleCount=“156” />   −<w:style w:type=“paragraph” w:default=“on” w:styleId=“Normal”> <w:name w:val=“Normal” />   −<w:rPr> <wx:font wx:val=“Times New Roman” /> <w:sz w:val=“24” /> <w:sz-cs w:val=“24” /> <w:lang w:val=“EN-US” w:fareast=“EN-US” w:bidi=“AR- SA” /> </w:rPr> </w:style>   − <w:style w:type=“character” w:default=“on”  w:styleId=“DefaultParagraphFont”> <w:name w:val=“Default Paragraph Font” /> <w:semiHidden /> </w:style>   −<w:style w:type=“list” w:default=“on” w:styleId=“NoList”> <w:name w:val=“No List” /> <w:semiHidden /> </w:style> </w:styles>   −<w:body>   −<w:p>   −<w:r> <w:t>The quick brown fox jumps over the lazy dog.</w:t> </w:r> </w:p>   −<w:p>   −<w:r> <w:t>The quick brown fox jumps over the lazy dog.</w:t> </w:r> </w:p> <w:p /> </w:body> </w:wordDocument>

According to embodiments of the present invention, consider for example that the user would like to insert a third paragraph into the document as follows “The quick brown fox jumps over the lazy dog” so that the inserted paragraph provides a final document as follows.

Para 1: The quick brown fox jumps over the lazy dog.

Para 2: The quick brown fox jumps over the lazy dog.

Para 3: The quick brown fox jumps over the lazy dog.

The following is an example XML structure showing the first two paragraphs of the document with the normal default style applied to them. According to this example, as shown in the following XML structure, the user inserts the third italicized paragraph into the document under a style called “My Style.” Because the paragraph is being inserted in an environment outside of the native Word Processing application, the logic of checking that the “My Style” style exists must be done manually. The XML file must be parsed to find the proper location of the style declarations, and then the style declarations must be parsed to guarantee that there is no conflict. Once this has been done, the “My Style” declaration can be entered. Now that the “My Style” declaration is entered, then the XML file must be parsed again to find the proper location for the paragraph itself. Since there was no conflict with the “My Style” declaration, the paragraph being inserted can still reference the “My Style” style. Otherwise, the paragraph itself would have to be altered to reference the proper style.

 <?xml version=“1.0” encoding=“UTF-8” standalone=“yes” ?>  <?mso-application progid=“Word.Document”?> − <w:wordDocument xmlns:w=“http://schemas.microsoft.com/office/word/2003/wordml” xmlns:wx=“http://schemas.microsoft.com/office/word/2003/auxHint” w:macrosPresent=“no”  w:embeddedObjPresent=“no”  w:ocxPresent=“no” xml:space=“preserve”>   −<w:styles> <w:versionOfBuiltInStylenames w:val=“4” /> <w:latentStyles w:defLockedState=“off” w:latentStyleCount=“156” />  −<w:style w:type=“paragraph” w:default=“on” w:styleId=“Normal”> <w:name w:val=“Normal” />   −<w:rPr> <wx:font wx:val=“Times New Roman” /> <w:sz w:val=“24” /> <w:sz-cs w:val=“24” /> <w:lang w:val=“EN-US” w:fareast=“EN-US” w:bidi=“AR- SA” /> </w:rPr> </w:style>   − <w:style w:type=“character” w:default=“on”  w:styleId=“DefaultParagraphFont”> <w:name w:val=“Default Paragraph Font” /> <w:semiHidden /> </w:style>   −<w:style w:type=“table” w:default=“on” w:styleId=“TableNormal”> <w:name w:val=“Normal Table” /> <wx:uiName wx:val=“Table Normal” /> <w:semiHidden />   −<w:rPr> <wx:font wx:val=“Times New Roman” /> </w:rPr>   −<w:tblPr> <w:tblInd w:w=“0” w:type=“dxa” />   −<w:tblCellMar> <w:top w:w=“0” w:type=“dxa” /> <w:left w:w=“108” w:type=“dxa” /> <w:bottom w:w=“0” w:type=“dxa” /> <w:right w:w=“108” w:type=“dxa” /> </w:tblCellMar> </w:tblPr> </w:style>   −<w:style w:type=“paragraph” w:styleId=“myStyle”> <w:name w:val=“myStyle” /> <w:basedOn w:val=“Normal” /> <w:rsid w:val=“000874C3” />   −<w:pPr> <w:pStyle w:val=“myStyle” /> </w:pPr>   −<w:rPr> <wx:font wx:val=“Times New Roman” /> <w:color w:val=“FF0000” /> </w:rPr> </w:style>   −<w:style w:type=“list” w:default=“on” w:styleId=“NoList”> <w:name w:val=“No List” /> <w:semiHidden /> </w:style> </w:styles>   −<w:body>   −<w:p>   −<w:r> <w:t>The quick brown fox jumps over the lazy dog.</w:t> </w:r> </w:p>   −<w:p>   −<w:r> <w:t>The quick brown fox jumps over the lazy dog.</w:t> </w:r> </w:p>   −<w:p>   −<w:pPr> <w:pStyle w:val=“myStyle” /> </w:pPr>   −<w:r> <w:t>The quick brown fox jumps over the lazy dog.</w:t> </w:r> </w:p> <w:p /> </w:body> </w:wordDocument>

As described above, according to embodiments of the present invention, an XML schema is provided which provides an XML element that may be used to markup and describe a particular text or data portion of a document such that style or other formatting properties applied to that text or data portion are treated separately from the remaining style or formatting properties associated with a document into which the text or data portion is inserted. So long as the document into which the text or data portion is inserted is operated by an application that may understand the XML schema associated with the text or data portion inserted into the document, the XML element wrapping the inserted text or data portion will be understood.

Below is a sample XML structure showing the addition of the third italicized paragraph “The quick brown fox jumps over the lazy dog” according to embodiments of the present invention. As shown in the following XML structure, the first two paragraphs are included in the document having style identification of “Times New Roman” and “Default Paragraph Font.” However, as shown in the following XML structure, the third paragraph being inserted into the document has been wrapped in an XML element called <cfChunk>. As should be appreciated, the element <cfChunk> is illustrative of an infinite number of names that could be provided to the element according to embodiments of the present invention by the creator of this particular XML structure. As should be understood, the element might similarly be called context free portion, cf portion, context free data, cfData, and the like. Inside the element <cfChunk> is contained the third paragraph “The quick brown fox jumps over the lazy dog” having a style identification of “My Style” and having a font identification of “italics.”

According to embodiments of the present invention, when the third paragraph “The quick brown fox jumps over the lazy dog” is copied or moved from a second document into a first document, the text or data portion moved points to or references an XML schema file that provides an XML parsing application associated with the first document access to the grammatical and other definitional rules associated with XML elements according to the schema file including the <cfchunk> element utilized for wrapping a text or data portion and for carrying with the text or data portion its own individual styles or other formatting properties. Accordingly, when the first document's XML parsing application encounters the element <cfChunk> that application may refer to the associated XML schema to learn that the style and other formatting designations contained in the structure wrapped inside the <cfchunk> element is to be treated particularly for a text or data portion being inserted into the first document and being associated with the <cfchunk> element. Accordingly, when the third paragraph is inserted into the first document according to embodiments of the present invention, as illustrated in the following sample XML structure, the style and other formatting properties associated with that text portion are honored by the application receiving the inserted text or data portion without regard to potentially conflicting style or other formatting properties associated with the document into which the text portion is inserted. The application does the necessary work to resolve any conflicts, and to properly associate the style reference for the paragraph with the appropriate style.

 <?xml version=“1.0” encoding=“UTF-8” standalone=“yes” ?> − <w:wordDocument xmlns:w=“http://schemas.microsoft.coin/office/word/2003/wordml” xmlns:wx=“http://schemas.microsoft.com/office/word/2003/auxHint” w:macrosPresent=“no” w:embeddedObjPresent=“no” w:ocxPresent=“no” xml:space=“preserve”>   −<w:styles> <w:versionOfBuiltInStylenames w:val=“4” /> <w:latentStyles w:defLockedState=“off w:latentStyleCount=“156” />   −<w:style w:type=“paragraph” w:default=“on” w:styleId=“Normal”> <w:name w:val=“Normal” />   −<w:rPr> <wx:font wx:val=“Times New Roman” /> <w:sz w:val=“24” /> <w:sz-cs w:val=“24” /> <w:lang w:val=“EN-US” w:fareast=“EN-US” w:bidi=“AR- SA” /> </w:rPr> </w:style>   − <w:style w:type=“character” w:default=“on”  w:styleId=“DefaultParagraphFont”> <w:name w:val=“Default Paragraph Font” /> <w:semiHidden /> </w:style>   −<w:style w:type=“list” w:default=“on” w:styleId=“NoList”> <w:name w:val=“No List” /> <w:semiHidden /> </w:style>   −<w:style w:type=“table” w:default=“on” w:styleId=“TableNormal”>  <w:name w:val=“Normal Table” /> <wx:uiName wx:val=“Table Normal” /> <w:semiHidden />   −<w:rPr> <wx:font wx:val=“Times New Roman” /> </w:rPr>   −<w:tblPr> <w:tblInd w:w=“0” w:type=“dxa” />   −<w:tblCellMar> <w:top w:w=“0” w:type=“dxa” /> <w:left w:w=“108” w:type=“dxa” /> <w:bottom w:w=“0” w:type=“dxa” /> <w:right w:w=“108” w:type=“dxa” /> </w:tblCellMar> </w:tblPr> </w:style> </w:styles>   −<w:body>   −<w:p>   −<w:r> <w:t>The quick brown fox jumps over the lazy dog.</w:t> </w:r> </w:p>   −<w:p>   −<w:r> <w:t>The quick brown fox jumps over the lazy dog.</w:t> </w:r> </w:p>   −<w:cfChunk>   −<w:styles>   −<w:style w:type=“paragraph” w:styleId=“myStyle”> <w:name w:val=“myStyle” /> <w:basedOn w:val=“Normal” /> <w:rsid w:val=“000874C3” />   −<w:pPr> <w:pStyle w:val=“myStyle” /> </w:pPr>   −<w:rPr> <wx:font wx:val=“Italics” /> <w:color w:val=“FF0000” /> </w:rPr> </w:style> </w:styles>   −<w:p>   −<w:pPr> <w:pStyle w:val=“myStyle” /> </w:pPr>   −<w:r> <w:t>The quick brown fox jumps over the lazy dog.</w:t> </w:r> </w:p> </w:cfChunk> <w:p /> </w:body> </w:wordDocument> Context-Free Document Portions with Alternate File Formats

As described above, according to prior methods and systems, when a portion of data or content is added to a document having a different file format as the receiving document, the receiving document may not be able to process the incoming portion in a manner that the incoming portion is properly displayed with appropriate formatting properties including styles, fonts, and the like. Or, when the incoming portion is of a different formatting type as the receiving document, the receiving document may fail to load the incoming portion altogether. For example, if a portion of data formatted according to the Hypertext Markup Language (HTML) is copied to a document formatted according to the Extensible Markup Language (XML), the HTML portion may fail to load because the application responsible for processing and displaying the document may not understand what the incoming portion of content is. As described above with reference to FIGS. 4 and 5, incoming portions of text or data may be wrapped in a <cfchunk> XML tag, and the XML annotation applied to the portion of text or data identifies formatting information such as styles, fonts and the like associated with the incoming portion of text or data so that a receiving XML-represented document may ascertain or resolve formatting properties to be applied to the incoming portion of text or data at the time the document is launched and the incoming portion of text or data integrated with (i.e., merged with, copied to, moved to, linked to ) the launched document.

According to another embodiment of the present invention, an XML <cfchunk> annotation is applied to an incoming portion of text, data or other content that provides self-describing properties to notify the receiving document and application as to alternative file format types associated with the incoming or referenced portion of text, data or other content to notify the receiving XML-represented document that the incoming portion is of a different file format type than is utilized for the receiving document. FIG. 6 is a simplified block diagram illustrating the insertion of context-free content portions having self-described alternative file formats into an XML-based document according to embodiments of the present invention. As illustrated in FIG. 6, an XML-represented document 610, for example, a word processing document, such as a memorandum or article, is illustrated. The XML document 610 is illustrated having a variety of XML structure applied to the document. For example, <heading> tags 615 are applied to the document for structuring heading information to be entered into the document. <Body> tags 620 are applied to the document for structuring text, data or other content to be inserted into the body of the document 610. As should be understood by those skilled in the art, the sample XML structure illustrated in FIG. 6 is not meant to represent well-formed XML tags and associated structure. The sample XML structure and information illustrated in FIG. 6 are for purposes of example only.

Referring still to FIG. 6, three <cfchunk> tags 625, 630, 635 have been applied to the XML document 610 within the <body> tag 620. According to embodiments of the present invention, the <cfchunk> tags 625, 630, 635 are utilized for annotating incoming portions of text, data or other content in a context-free manner to allow the incoming portions to be self-describing to the XML document 610. As described above with reference to FIGS. 4 and 5, an application with which the XML document 610 is generated and/or edited calls on an XML parsing application either integrated with the application in use or called upon by the application in use to parse the XML structure applied to the XML document 610.

According to embodiments of the present invention, when the XML parsing application parses the XML <cfChunk> tags 625, 630, 635 associated with portions 640, 645, 650, respectively, the parsing application determines the specified file format types and formatting information applied to each incoming portion of content. For example, the first incoming portion 640 that is to be inserted into the body of the XML document 610 has been associated with a <cfChunk1> tag and identifies the file format type of the incoming portion as HTML. A style type of “style: 1” is also identified. Accordingly, the application, for example, a word processing application, responsible for generating, editing and displaying the XML document 610, learns through parsing the XML structure applied to the document 610 that the inserted content portion 640 is formatted according to HTML and bears a formatting style of “style: 1.” Accordingly, the application in use for generating and/or editing the XML-represented document 610 may process the incoming content portion 640 according to the file format type and style associated with the incoming portion. For example, with reference to the incoming portion 640, the receiving application will know that the incoming portion must be processed, read, and displayed according to the Hypertext Markup Language, or that the incoming portion must be transformed from the an HTML file format into another file format type suitable for processing by the receiving application. Similarly, the receiving application will know that the incoming portion should be displayed with formatting properties, for example, fonts, styles, etc. associated with the identified formatting property of “style: 1.”

As illustrated in FIG. 6, a second incoming content portion 645 is illustrated. The second incoming portion 645 is illustrated as having a file format type of rich text formatting (RTF) in a style identified as “style: 4.” As with the incoming portion 640, the information used for self-describing the incoming portion of content may be utilized by the receiving or consuming application for understanding the file format type associated with the incoming portion and for understanding any associated formatting properties applied to the incoming content. Similarly, a third incoming portion 650 is illustrated having an associated binary file format type and an associated style of “style: 2.” As with the other incoming content portions, the receiving or consuming application may utilize the identified file format type and other information such as the identified style properties for receiving and processing the incoming content portion.

According to this embodiment, the receiving or consuming application, for example, a word processing application, may utilize the incoming portions of content in view of the file format types associated with those portions. According to prior methods and systems, the incoming portions may fail to load by the receiving application, or even if the incoming portions successfully load by the receiving application, the associated text, data or other content may be processed incorrectly. For example, the incoming portion may be displayed in an unsatisfactory manner. Because the receiving application may ascertain the original file format type of the incoming content, the receiving application may take appropriate action such as transforming the incoming content, or such as calling on software programming necessary for understanding, consuming, and utilizing the incoming content. For example, if the incoming content is formatted according to HTML, the receiving application may either transform the incoming content prior to utilizing the content, or the receiving application may access code necessary for utilizing, for example, displaying, the incoming content. Accordingly, as the receiving application resolves associated formatting properties for the incoming content, as described above with reference to FIGS. 4 and 5, according to embodiments of the present invention, the receiving application may also resolve alternative file format types associated with the incoming content.

According to an embodiment of the present invention, a software application responsible for receiving or consuming the content portions described herein, for example, a word procession application, a spreadsheet application, a slide presentation application, a desktop publishing application and the like, may likewise create or generate the context free portions of data 640, 645, 650 for use by other applications. When a portion of data is saved by such an application, or when a portion of data is copied for pasting to a document operated by another document, the application in use for generating the context free portion may apply a <cfChunk> annotation to the data, and the application may save properties to the portion of data for identifying a file format associated with the portion of data, as well as, other properties such as formatting (e.g., boldfacing, italics, font, etc.). For example, if the application generating the context free portion 640, 645, 650 generates data according to an HTML format, then the context free portions of data generated for use by other applications may be annotated to identify HTML as the file format associated with the context free portion of data. When a consuming application receives the data, as described above, the consuming application may read and use the context free portion according to the associated file format and other formatting properties applied to the portion of data by the generating application.

Referring now to FIG. 7, and according to another embodiment of the present invention, a receiving document 710 and one or more incoming content portions 730, 735, 740 may be contained in an electronic file container 700. For example, the file container 700 may be representative of a file format such as a .ZIP file format. According to embodiments, if the file container 700 is selected or opened, the XML receiving document 710 and each of the associated content portions 730, 735, 740 may be identified and visually represented as separate files. According to this embodiment, each incoming content portion 730, 735, 740 is not inserted or populated in line into a receiving document 710, as described above with reference to FIG. 6, but instead the receiving document 710 references a relationship file 750 which, in turn, points to the incoming content portions and provides information to the receiving document 710 and to an application responsible for processing the receiving document 710 for utilizing the incoming content portions.

As illustrated in FIG. 7, the XML document 710 is representative of a receiving document being generated by an author/editor, and the content portions 730, 735, 740 are representative of incoming content portions for merging with the receiving document 710. The receiving document 710 includes three content references 715, 720, 725. According to embodiments of the present invention, the file container 700 is linked to a relationship file 750, which contains a relationship tree 755 illustrating the relationship between the receiving document 710 and the incoming content portions which are to be merged with the receiving document 710 upon document load and/or launch by the receiving document application, for example, a word processing application, a spreadsheet application, a slide presentation application, and the like.

Referring to the relationship file 750, each content reference identified in the XML document 710 points to an associated incoming content portion. According to embodiments of the present invention, when a software application responsible for operating the receiving document 710, for example, a word processing application, spreadsheet application, slide presentation application, and the like loads the receiving document 710, the document 710 is parsed by an associated parsing application, for example, an XML parser, for structure applied to the receiving document 710. When each reference 715, 720, 730 is parsed, the receiving application references the relationship file 750 for determining what incoming or associated content portion is pointed to by the identified reference. For example, when the XML document 710 is parsed, the first reference 715 is found to point to a first content portion 730, which is a content portion having a file format type of HTML, for example. When the second reference 720 is parsed in the XML document 710, reference to the relationship file 750 determines that the second reference 720 points to a second incoming content portion 735 having a file format of RTF. Similarly, when the third reference 725 is parsed in the receiving document 710, a reference to the associated relationship file 750 shows that the third reference 725 points to a third incoming portion 740 having a binary file format type. Once all information such as file format types associated with referenced content is resolved, the receiving application may merge the pointed-to content portions with the receiving document for displaying a merged document. For a detailed discussion of the containment and association of components of a document as described with reference to FIG. 7, see U.S. patent application, entitled “Improved Management And Use Of Data In A Computer-Generated Document, filed Dec. 20, 2004, Ser. No. 11/019,088, which is incorporated herein by reference as if fully set out herein.

As described herein, methods and systems are provided for inserting a portion of text or data into a document or associating the portion of text or data with the document where the inserted or associated portion of text or data carries with it its own file format type and other formatting properties, such as specified styles, fonts, list types, and the like to allow a receiving application to process the portion of text or data properly. It will be apparent to those skilled in the art that various modifications or variations may be made in the present invention without departing from the scope or spirit of the invention. Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. 

1. A computer-readable medium on which is stored instructions which when executed by a computer perform a method of integrating a content portion in a receiving document based on self-describing properties associated with the content portion, comprising: receiving a content portion having a self-describing property identifying a file format with which the content portion is formatted; receiving the content portion at a receiving application for integrating the content portion with a computer-generated document; at the receiving application, parsing the self-describing property identifying the file format with which the content portion is formatted, wherein the self-describing property comprises at least one markup language element; processing the content portion according to the file format with which the content portion is formatted; validating the at least one markup language element against at least one schema file attached to the computer-generated document, wherein the schema file comprises rules defining valid annotations of the computer-generated document with markup language elements listed in the at least one schema file; and integrating the content portion with the computer-generated document, wherein integrating the content portion comprises annotating the computer-generated document with the self-describing property comprising the at least one markup language element.
 2. The computer-readable medium of claim 1, whereby receiving the content portion having a self describing property identifying a file format with which the content portion is formatted includes receiving at the receiving application an indication of a selection for integrating the content portion with the computer-generated document.
 3. The computer-readable medium of claim 1, whereby parsing the self-describing property identifying the file format with which the content portion is formatted includes determining a file format with which the content portion is formatted and determining any processing requirements for integrating the content portion with the computer-generated document.
 4. The computer-readable medium of claim 3, whereby determining any processing requirements for integrating the content portion with the computer-generated document includes determining whether the content portion must be transformed into a different file format prior to integrating the content portion with the computer-generated document.
 5. The computer-readable medium of claim 4, whereby processing the content portion according to the file format with which the content portion is formatted includes transforming the content portion into the different file format prior to integrating the content portion with the computer-generated document.
 6. The computer-readable medium of claim 3, whereby determining any processing requirements for integrating the content portion with the computer-generated document includes determining whether the receiving application requires additional functionality for integrating the content portion with the computer-generated document.
 7. The computer-readable medium of claim 6, whereby processing the content portion according to the file format with which the content portion is formatted includes: accessing additional functionality by the receiving application; and processing the content portion with the additional functionality.
 8. The computer-readable medium of claim 1, whereby integrating the content portion with the computer-generated document includes copying the content portion into the computer-generated document after processing the content portion according to the file format with which the content portion is formatted.
 9. The computer-readable medium of claim 1, further comprising storing the computer-generated document and the content portion in an electronic file container; and providing a relationship representation showing how the content portion is related to the computer-generated document.
 10. The computer-readable medium of claim 9, whereby providing a relationship representation showing how the content portion is related to the computer-generated document includes showing a location in the computer-generated document at which the content portion is to be integrated with the computer-generated document.
 11. The computer-readable medium of claim 10, whereby integrating the content portion with the computer-generated document includes: linking the content portion to a given location in the computer-generated document; and calling the content portion for presenting the content portion at the given location after processing the content portion according to the file format with which the content portion is formatted.
 12. The computer-readable medium of claim 1, prior to receiving a content portion having a self-describing property identifying a file format with which the content portion is formatted, further comprising: generating a content portion for use by a receiving application; and applying a self-describing property to the content portion for identifying to the receiving application a file format with which the content portion is formatted.
 13. A method of integrating a content portion in a receiving, document based on self-describing properties associated with the content portion, comprising: receiving a content portion having a self-describing property identifying a file format with which the content portion is formatted; receiving the content portion at a receiving application for integrating the content portion with a computer-generated document; at the receiving application, parsing the self-describing property identifying the file format with which the content portion is formatted to determine the file format with which the content portion is formatted and to determine a relationship between the content portion and the computer-generated document, wherein the self-describing property comprises at least one markup language element; storing the computer-generated document and the content portion in an electronic file container; and providing a relationship representation showing how the content portion is related to the computer-generated document; processing the content portion according to the file format with which the content portion is formatted; validating the at least one markup language element against at least one schema file attached to the computer-generated document, wherein the schema file comprises rules defining valid annotations of the computer-generated document with markup language elements listed in the at least one schema file; and integrating the content portion with the computer-generated document, wherein integrating the content portion comprises annotating the computer-generated document with the self-describing property comprising the at least one markup language element.
 14. The method of claim 13, whereby integrating the content portion with the computer-generated document includes: linking the content portion to a given location in the computer-generated document; and calling the content portion for presenting the content portion at the given location after processing the content portion according to the file format with which the content portion is formatted.
 15. A computer-readable medium on which is stored instructions which when executed by a computer perform a method of integrating a content portion in a receiving document based on self-describing properties associated with the content portion, comprising: receiving a content portion having a self-describing property identifying a file format with which the content portion is formatted; receiving the content portion at a receiving application for integrating the content portion with a computer-generated document; at the receiving application, parsing the self-describing property identifying the file format with which the content portion is formatted, wherein the self-describing property comprises at least one markup language element, wherein the self-describing property comprises at least one markup language element; processing the content portion according to the file format with which the content portion is formatted; validating the at least one markup language element against at least one schema file attached to the computer-generated document, wherein the at least one schema file comprises rules defining valid annotations of the computer-generated document with markup language elements listed in the at least one schema file and wherein validating comprises determining whether the at least one markup language element violates the rules of the at least one schema file, the rules comprising at least one of a maximum character length of a text entry and an insertion of an invalid markup language element; generating an error message upon determining the receipt of invalid markup language in the computer-generated document; and integrating the content portion with the computer-generated document wherein integrating the content portion comprises annotating the computer-generated document with the self-describing property comprising the validated at least one markup language element.
 16. The computer-readable medium of claim 15, whereby receiving the content portion having a self-describing property identifying a file format with which the content portion is formatted includes receiving at the receiving application an indication of a selection for integrating the content portion with the computer-generated document.
 17. The computer-readable medium of claim 15, whereby parsing the self-describing property identifying the file format with which the content portion is formatted includes determining a file format with which the content portion is formatted and determining any processing requirements for integrating the content portion with the computer-generated document.
 18. The computer-readable medium of claim 17, whereby determining any processing requirements for integrating the content portion with the computer-generated document includes determining whether the content portion must be transformed into a different file format prior to integrating the content portion with the computer-generated document.
 19. The computer-readable medium of claim 15, further comprising storing the computer-generated document and the content portion in an electronic file container; and providing a relationship representation showing how the content portion is related to the computer-generated document. 